test/nuxt/composables/use-package-comparison.spec.ts (2)

145-168: "Perfect package" test omits description, leaving the +10 quality bonus untested.

The computeHealthScore function awards +10 quality points when data.package.description is truthy (line 372 in usePackageComparison.ts). This test intends to verify a "perfect" package but the makeData() override doesn't include a description field, so that scoring path is never exercised.

Consider adding description to the package object to truly test the perfect-score scenario:

🔧 Suggested fix

       const score = computeHealthScore(
         makeData({
+          package: { name: 'test', version: '1.0.0', description: 'A test package' },
           metadata: {
             lastUpdated: new Date().toISOString(),
             license: 'MIT',
           },

---

132-138: Consider hoisting makeData outside the describe block.

The static analysis correctly flags that makeData doesn't capture any variables from its parent scope. Moving it to module level (or at least outside the inner describe) would satisfy the linter and make it reusable for additional test cases.

test/nuxt/composables/use-package-comparison.spec.ts (1)

131-137: Consider moving makeData to module level.

The helper doesn't capture any variables from its enclosing scope, so it could be hoisted to module level for clearer organisation and to resolve the linter warning.

♻️ Proposed refactor

Move the helper above the describe('usePackageComparison') block:

+function makeData(overrides: Partial<PackageComparisonData> = {}): PackageComparisonData {
+  return {
+    package: { name: 'test', version: '1.0.0' },
+    directDeps: 2,
+    ...overrides,
+  }
+}
+
 describe('usePackageComparison', () => {
   afterEach(() => {
     vi.unstubAllGlobals()
   })
   // ...
-  function makeData(overrides: Partial<PackageComparisonData> = {}): PackageComparisonData {
-    return {
-      package: { name: 'test', version: '1.0.0' },
-      directDeps: 2,
-      ...overrides,
-    }
-  }